Control of uplink data transmission

ABSTRACT

A method for control of data transmission in a wireless communication system includes receiving, by an application, from a modem, information indicative of a radio coverage condition, where a user equipment (UE) includes the application and the modem; based on the received information, determining that the UE is in an enhanced coverage state; and in response to the determining, controlling uplink data transmission by the modem to reduce power consumption of the UE.

This application is a continuation of U.S. patent application Ser. No.16/529,605 filed on Aug. 1, 2019, which is a continuation of U.S. patentapplication Ser. No. 16/119,044 filed on Aug. 31, 2018, and issued asU.S. Pat. No. 10,405,279 on Sep. 3, 2019, which is a continuation ofU.S. patent application Ser. No. 15/419,321 filed on Jan. 30, 2017, andissued as U.S. Pat. No. 10,070,393 on Sep. 4, 2018, the contents ofwhich are hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates to data transmission in wireless communicationsystems and, more specifically, to uplink data transmission.

BACKGROUND

A wireless communication system can include an enhanced coveragefunctionality to extend a cell coverage area of a base station. The cellcoverage area can be extended by repeated data transmissions. Forexample, a device in extended coverage areas can transmit datarepeatedly so that the base station receives enough radio energy todetect data. In Long-Term Evolution (LTE) wireless systems, a deviceconfigured with an enhanced coverage functionality can have a maximumnumber of repetitions, for example, between 8 to 32 if the device is ina coverage enhancement mode A or between 192 to 2048 if the device is ina coverage enhancement mode B. However, repeated data transmissions canlead to a high power consumption at the device.

For devices whose battery can be easily or frequently recharged,benefits of using the enhanced coverage functionality to gain morecoverage may offset impacts of extra battery consumption. However, for adevice that cannot be recharged frequently or cannot be recharged atall, for example, an asset tracker device that can remain operationalwithout maintenance for a number of years, battery consumption issensitive and the extra battery consumption could outweigh the gain incoverage.

DESCRIPTION OF DRAWINGS

FIG. 1 is an example wireless communication system that includescontrolling of data transmission in enhanced coverage states accordingto some implementations.

FIG. 2 is a first flow diagram illustrating solution 1 for controllingdata transmission in enhanced coverage states according to someimplementations.

FIG. 3 is a flowchart illustrating a first example method for solution 1of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 4 is a flow diagram illustrating solution 2 for controlling datatransmission in enhanced coverage states according to someimplementations.

FIG. 5 is a flowchart illustrating a first example method for solution 2of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 6 is a flowchart illustrating a second example method for solution2 of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 7 is a flowchart illustrating a second example method for solution1 of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 8 is a flowchart illustrating a third example method for solution 2of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 9 is a second flow diagram illustrating solution 1 for controllingdata transmission in enhanced coverage states according to someimplementations.

FIG. 10 is a third flow diagram illustrating solution 1 for controllingdata transmission in enhanced coverage states according to someimplementations.

FIG. 11 is a flowchart illustrating a third example method for solution1 of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 12 is a flowchart illustrating a fourth example method for solution2 of controlling data transmission in enhanced coverage states accordingto some implementations.

FIG. 13 is a flowchart illustrating a fifth example method for solution2 of controlling data transmission in enhanced coverage states accordingto some implementations.

FIGS. 14A-14C show an example description of an attention (AT) commandto enable solution 1 according to some implementations.

FIGS. 15A-15B show a first example description of an AT command toenable solution 2 according to some implementations.

FIG. 16 shows a second example description of an AT command to enablesolution 2 according to some implementations.

FIG. 17 shows an example information element (IE) or field includingconfiguration information for transmission restrictions according tosome implementations.

FIGS. 18A-18D show a first example description of includingconfiguration parameters for transmission restrictions in an AttachAccept message according to some implementations.

FIG. 19 shows a second example description of including configurationparameters for transmission restrictions in an Attach Accept messageaccording to some implementations.

FIGS. 20A-20H show an example description of including configurationparameters for transmission restrictions in an Activate Default evolvedpacket system (EPS) Bearer Context Request message according to someimplementations.

FIG. 21 shows an example radio resource control (RRC) IE includingconfiguration information of transmission restrictions according to someimplementations.

FIG. 22 is a schematic illustrating an example network node according tosome implementations.

FIG. 23 is a schematic illustrating an example user equipment (UE)device according to some implementations.

FIGS. 24A-24B show an example of a solicited AT command according tosome implementations.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

The present disclosure is directed to the control of data transmissionwhen a device is in an enhanced coverage state. Various modifications tothe disclosed implementations will be readily apparent to those ofordinary skill in the art, and described principles may be applied toother implementations and applications without departing from scope ofthe disclosure.

In wireless communication systems, a device can be in an enhancedcoverage state if the device uses an enhanced coverage functionality toaccess a base station. For example, as will be discussed below, a devicecan be in an enhanced coverage state if the device is in certaincoverage enhancement mode(s), coverage enhancement level(s), or coverageclass(es), a strength or quality of a radio signal received at thedevice is below a threshold, or a number of repetitions for datatransmission is higher than a threshold. When the device is in anenhanced coverage state, the device can control uplink data transmissionto reduce power consumption. The device can refrain from sending uplinkdata based on information such as data type (e.g., emergency ornon-emergency data), Quality of Service (QoS) associated with the data,whether the device is moving, whether a timer or counter associated withthe transmission control has expired, battery level, or whether thedevice is plugged into a power supply. For example, when the device isin an enhanced coverage state, the device can refrain from sendinguplink data if the data carries non-emergency location information orthe device is not plugged into a power supply.

FIG. 1 is an example wireless communication system 100 that includescontrolling of data transmission in enhanced coverage states accordingto some implementations. The example communication system 100 includes auser equipment (UE) or device 102 and a wireless network including abase station 104, where the device 102 is in the cell coverage of thebase station 104. The coverage area of the base station 104 includes anormal coverage area within a normal coverage boundary 106 and anenhanced coverage area between the normal coverage boundary 106 and anenhanced coverage boundary 108. The device 102 can communicate with thebase station 104 using an enhanced coverage functionality. For example,when transmitting data 110 to the base station 104, the device 102 canuse a higher number of repetitions in the enhanced coverage area than inthe normal coverage area.

In Long-Term Evolution (LTE) wireless systems, the enhanced coveragefunctionality (see 3GPP TS 36.300) includes the following:

-   -   In radio resource control (RRC) idle mode (RRC_IDLE), four        coverage enhancement (CE) levels 0, 1, 2 and 3 are defined for        physical random access channel (PRACH) resource selection.    -   In RRC connected mode (RRC_CONNECTED), two enhanced CE modes,        mode A (low/medium coverage) and mode B (extreme coverage), are        supported for transmitting data to the base station.

A set of PRACH resources (e.g. time, frequency, preamble), eachassociated with a given CE level, is provided in system informationblocks (SIBs). The number of PRACH repetitions and the number of maximumpreamble transmission attempts per CE level are also provided in SIBs.The initial CE level may be provided in SIBs and indicates the initialPRACH CE level to be used at random access by UEs in that cell. If notprovided, the UE selects the PRACH CE level based on the measuredreference signal received power (RSRP) level compared to RSRP thresholdsprovided in SIBs (see 3GPP TS 36.321). The CE mode to be used by a UE inenhanced coverage is provided when the UE is entering connected mode,typically in the RRCConnectionReconfiguration or the RRCConnectionResumemessage. Information about the number of repetitions to be used for agiven signal or on a given channel are either provided in SIBs (per CEmode), as part of downlink control information (DCI), or in a dedicatedmessage when the UE is entering the connected mode. For example, themaximum number of repetitions that can be configured by the network fora physical uplink shared channel (PUSCH) are between 8 and 32 for CEmode A and between 192 and 2048 for CE mode B. In other words, Mode Bprovides further enhanced coverage than Mode A, requiring higherrepetitions numbers and therefore higher battery consumption.

An enhanced coverage functionality can also be defined for narrow bandInternet of Things (NB-IoT) UEs and is characterized by different CElevels and different repetition levels that can be configured by thenetwork. For example, up to 3 narrowband PRACH (NPRACH) resources can beconfigured in a cell, defined by at most two RSRP thresholds. Thedifferent NPRACH resources are mapped to corresponding CE levels. Thenetwork may indicate an initial number of PRACH repetitions to be usedby the UE, or the starting CE level can be provided by upper layers, inwhich case the UE considers itself to be in the corresponding CE levelregardless of the measured RSRP. The maximum number of repetitions for agiven channel is configured by the network.

An enhanced coverage functionality is also an inherent part of theextended coverage GSM for Internet of Things (EC-GSM-IoT) (see 3GPP TS43.064), including up to five coverage classes (CCs), CC1, CC2, CC3,CC4, and, if applicable, CC5, where CC1 corresponds to a typical generalpacket radio service (GPRS)/enhanced GPRS (EGPRS) coverage range. In anidle mode, the EC-GSM-IoT mobile station (MS) selects the CC to be usedand indicates the selected CC to the network, while in Packet TransferMode, the network performs CC selection and communicates the CC to theMS. A predefined number of logical channel specific blind physical layertransmissions is used to support a certain level of extended coverage.

In some cases, when the device is in an idle mode, the UE autonomouslydecides on the radio coverage level (if the UE supports the enhancedcoverage functionality) based on radio measurement criteria. When thedevice enters a connected mode, the network configures which enhancedcoverage mode or repetition level the UE shall use based on radiomeasurements sent by the device and/or on other considerations. For UEssupporting the enhanced coverage functionality, it is possible for thenetwork to decide that the UE shall not use the enhanced coveragefeature based on subscription information (for example the possibilityto use enhanced coverage may be allowed only for premium subscriptionusers) or for other reasons.

In the described approach, an application can receive from a modeminformation indicative of a radio coverage condition, where a userequipment (UE) includes the application and the modem. Based on thereceived information, the application can determine that the UE is in anenhanced coverage state. In response to the determining, the applicationcan control uplink data transmission by the modem to reduce powerconsumption of the UE. The received information can include at least oneof a coverage enhancement level, a coverage enhancement mode, a coverageclass, a data repetition indicator, a signal strength, or a signalquality. Controlling uplink data transmission can include refrainingfrom sending uplink data when at least one of the following occurs: theUE is in one of a set of predefined coverage enhancement levels,coverage classes, or coverage enhancement modes, the data repetitionindicator is above a predefined repetition threshold, a signal strengthat the UE is below a predefined signal strength threshold, or a signalquality at the UE is below a predefined signal quality threshold; theuplink data has a predefined data type; the uplink data is associatedwith at least one of a predefined Quality of Service (QoS) indicator, apredefined priority level, or a predefined bit rate information; apredefined timer associated with the transmission controlling has notexpired; a counter associated with the transmission controlling hasreached a predefined counter threshold; the UE is moving; a batterylevel of the UE is higher than a first threshold; a battery level of theUE is lower than a second threshold; or the UE is not plugged into apower outlet.

In some implementations, the application can receive speed informationfrom a location sensor or an accelerometer of the UE. Based on the speedinformation, the application can determine whether the UE is moving. Thespeed information can be received responsive to a query sent by theapplication to the location sensor or the accelerometer. In someimplementations, the application can receive battery information from anoperating system, a device interface, or a battery sensor of the UE.Based on the battery information, the application can determine whetherthe battery level of the UE is higher than the first threshold or lowerthan the second threshold, or whether the UE is plugged into a poweroutlet. The battery information can be received responsive to a querysent by the application to the operating system, the device interface,or the battery sensor. The UE can receive from a network nodeconfiguration information including an indication that the UE isconfigured to control uplink data transmission and parameters associatedwith controlling the uplink data transmission. In some implementations,the application can receive information indicative of a radio coveragecondition responsive to a query sent by the application to the modem.The query from the application to the modem for information indicativeof a radio coverage condition can be conveyed in a first attention (AT)command. The information indicative of a radio coverage condition fromthe modem to the application can be conveyed in a second AT command. Insome cases, the application receives from the modem informationindicative of the radio coverage condition when the radio coveragecondition changes.

The data transmission control in enhanced coverage states according tomethods and systems described herein can reduce a device's powerconsumption when the device is in an enhanced coverage state. FIGS. 2-24and associated descriptions provide additional details for theseimplementations.

Turning to a general description of the elements, a UE (or device) 102may be referred to but is not limited to as an IoT device,machine-to-machine (M2M) device, machine type communication (MTC)device, mobile electronic device, user device, mobile station,subscriber station, portable electronic device, mobile communicationsdevice, wireless modem, push-to-talk (PTT) dispatch console, or wirelessterminal. Examples of a UE may include but are not limited to a cellularphone, personal data assistant (PDA), smart phone, PTT dispatch console,laptop, tablet personal computer (PC), pager, portable computer,portable gaming device, wearable electronic device, test equipment,gambling machine, car/vehicle, notice board, home appliance, M2M/IoTelectronic modules, or other mobile communications device havingcomponents for communicating voice or data via a wireless communicationnetwork. The wireless communication network may include a wireless linkover at least one of a licensed spectrum and an unlicensed spectrum.

Other examples of a UE include mobile and fixed electronic devices. A UEmay include a Mobile Equipment (ME) device and a removable memorymodule, such as a Universal Integrated Circuit Card (UICC) that includesa subscriber identity module (SIM), a Universal SIM (USIM), or aRemovable User Identity Module (R-UIM). The term “UE” can also refer toany hardware or software component that can terminate a communicationsession for a user. In addition, the terms “user equipment,” “UE,” “userequipment device,” “user agent,” “UA,” “user device,” “mobile station,”“MS,” “mobile device,” and “module” can be used synonymously herein.

The wireless communication network may include one or a plurality ofradio access networks (RANs), other access networks such as fixedEthernet or IEEE 802.11 WLAN, core networks (CNs), and externalnetworks. The RANs may include one or more radio access technologies. Insome implementations, the radio access technologies may be but are notlimited to global system for mobile communication (GSM), EC-GSM-IoT,Interim Standard 95 (IS-95), Universal Mobile Telecommunications System(UMTS), CDMA2000 (Code Division Multiple Access), Evolved UMTS, LTE,LTE-Advanced, New Radio (NR), or NB-IoT. In some instances, the corenetworks may be evolved packet cores (EPCs) or next generation cores (NGCores).

A RAN is part of a wireless telecommunication system which implements aradio access technology, such as GSM, UMTS, CDMA2000, 3GPP LTE, 3GPPLTE-Advanced (LTE-A), NB-IoT, and EC-GSM-IoT. In many applications, aRAN includes at least one base station. A base station (e.g., the basestation 104) may be a radio base station that may control all or atleast some radio-related functions in a fixed part of the system. Thebase station may provide radio interface within its coverage area or acell for a UE to communicate. The base station or plurality of basestations may constitute the cellular network to provide a wide area ofcoverage. The base station directly or indirectly communicates with oneor a plurality of UEs, other base stations, and one or more core networknodes.

While elements of FIG. 1 are shown as including various component parts,portions, or modules that implement the various features andfunctionality, nevertheless these elements may instead include a numberof sub-modules, third-party services, components, libraries, and such,as appropriate. Furthermore, the features and functionality of variouscomponents can be combined into fewer components as appropriate. Thedescribed approach may be implemented using other methods or elementsconsistent with the scope of this disclosure. Although in some of thedescription in this disclosure LTE and GSM are used as an example, aswill be understood by those of ordinary skill in the art, the describedapproach can also be used for other wireless communication systems andradio access technologies (RATs), such as 3GPP UMTS terrestrial radioaccess network (UTRAN), IEEE (e.g. 11.x, WiFi, WiMax), CDMA2000, andfifth generation (5G). In this disclosure, “uplink message,” “uplinkdata,” and “uplink data transmission” are used as general terms for anyuser plane type of information that would encompass one or moremessage(s), a structured or unstructured data stream, or any otherequivalent terminology. Further, coverage enhancement level isinterchangeable with enhanced coverage level, and coverage enhancementmode is interchangeable with enhanced coverage mode. In addition, insome implementations, various steps of flow diagrams and flowcharts inFIGS. 2-13 may be run in parallel, in combination, in loops, or in anyorder.

Solution 1: Refraining from mobile-originated data transmission if thedevice is in an enhanced coverage state: application obtains informationand decides whether to refrain from data transmission

FIG. 2 is a first flow diagram 200 illustrating solution 1 forcontrolling data transmission in enhanced coverage states according tosome implementations. The flow diagram 200 includes an application 202and a modem 204 at a device. The application 202 determines (or isconfigured so, as will be discussed below) that the device can refrainfrom transmitting uplink data to the network if the device is in anenhanced coverage state. The data refrained from transmission couldeither be dropped or discarded (e.g., location information that wouldbecome obsolete after a time duration), or be retained and sent later(e.g. when the restriction on uplink data transmission is revoked). Themodem 204 has knowledge of the radio coverage condition for the device(e.g., the currently applicable CE mode/level or coverage class, radiosignal strength or quality such as received signal strength indicator(RSSI), received signal code power (RSCP), or RSRP, a number ofrepetitions for data transmission, or other radio link information). Theapplication 202 can send a query 206 to the modem 204 for information orstatus of the radio coverage condition. Based on the status report 208from the modem 204, the application 202 determines whether to senduplink data or not. The application can apply any conditions fortransmission restrictions. For example, the application 202 may decidenot to send data if a device CE level/mode or coverage class is one in aset of predefined CE levels/modes or coverage classes, if a number ofdata repetitions is above a predefined repetition threshold, a signalstrength at the device is below a predefined signal strength threshold,or a signal quality at the device is below a predefined signal qualitythreshold. For instance, the application 202 can decide not to transmituplink data if the device/modem is in the enhanced coverage level 1, 2,or 3.

In some implementations, the query 206 and status report 208 can be anattention (AT) command and response (see 3GPP TS 27.007), respectively.The AT commands and responses enable sending information or instructionsbetween application (i.e. terminal equipment (TE)) and modem (i.e.Mobile Terminal (MT)), through a terminal adaptor (TA). Responses can betriggered following AT commands (one response to each received ATcommand), or unsolicited (e.g., activated and/or configured by an ATcommand; multiple responses can be sent corresponding to that ATcommand, and a response is sent every time the information at the modemchanges or other conditions, that may have been configured by the ATcommand, are satisfied at the modem). In some cases, AT responses arealso called AT commands. The query 206 and status report 208 can alsouse other application programming interfaces (APIs) instead of ATcommand/response.

Table 1 lists examples of query 206 from the application 202 to themodem 204, and examples of associated reported status 208 from the modem204 to the application 202:

TABLE 1 Examples of query from application to modem Example queries fromPossible reported application to status from modem to modem applicationProvide the enhanced Enhanced coverage level is 0 coverage levelEnhanced coverage level is 1 Enhanced coverage level is 2 Enhancedcoverage level is 3 Is the enhanced Yes coverage level above 2? No Isthe RSSI of the Yes serving cell above 3 dB? No Provide the RSSI of RSSI= −1 dB the Primary Serving Cell RSSI = 1 dB RSSI = 3 dB RSSI = 5 dBRSSI = 7 dB Provide a status every Enhanced coverage level has changedto 0 time that the enhanced Enhanced coverage level has changed to 1coverage level changes Enhanced coverage level has changed to 2 Enhancedcoverage level has changed to 3 Provide a status every Enhanced coveragetime that the enhanced level changed from (2, 3) coverage level goes to(0, 1) between (0, 1) and (2, 3) Enhanced coverage level changed from(0, 1) to (2, 3)Note that for the last two examples in Table 1, one query may triggermore than one status report because the modem 204 sends a status reportevery time the enhanced coverage level changes. In some implementations,the query 206 is optional for these two examples. For example, as willbe discussed below, the application 202 can use an AT command tosubscribe or register to the modem 204 for receiving notifications ofenhanced coverage level change, and the modem 204 will send unsolicitedstatus reports to the application 202 every time the enhanced coveragelevel changes. Alternatively, sending unsolicited notifications by themodem 204 to the application 202 can be pre-configured in the modem.

In some implementations, a device in an enhanced coverage state is adevice conforming to, for example (but not limited to), one or more ofthe following criteria:

-   -   The device is in enhanced coverage mode A or mode B for LTE UEs,        the currently selected CE level is part of an identified set of        possible CE levels, or the currently selected coverage class is        part of an identified set of possible coverage classes. Since        for LTE UEs enhanced coverage mode B allows transmission in more        degraded coverage than mode A but at the price of higher power        consumption, the device could decide to not transmit one or more        uplink message if the device is in mode B, but transmit the        message when possible if the device is in mode A.    -   A link budget or radio link power/quality (e.g. based on a RSSI,        RSCP, or RSRP) is below an identified threshold. This criterion        allows to specify a consistent behavior irrespective of the        device category (e.g., NB-IoT and non NB-IoT UEs).    -   A number of repetitions, possibly associated to a given channel        type (e.g. a PRACH or MTC PRACH (MPRACH) repetitions number        configured by the network), is above a predefined threshold.

In some implementations, the modem 204 generates an event triggered ATcommand to notify the application 202 that a change in enhanced coveragestatus has been detected (any change, or one or more specificchange(s)). The application 202 is able to use an AT command tosubscribe or register to receiving such notifications from the modem204. If the modem 204, in the course of operation, has detected suchchanges in enhanced coverage, it would be useful for the application 202to be informed. The application 202 can store the latest enhancedcoverage status for the UE. This might at a later stage prevent theapplication 202 from inquiring the modem 204 for the coverageinformation. Note that there is a power cost in the modem for obtainingthe enhanced coverage status. In the event the application decides notto send data (e.g., a low priority packet) because of the poor coverage,the power for obtaining the enhanced coverage status is wasted.

FIG. 3 is a flowchart illustrating a first example method 300 forsolution 1 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 300 starts at block 302,where the application inquires the modem, e.g., using an AT command, forinformation of the enhanced coverage level or radio coverage condition.As discussed above, block 302 is optional if the application subscribesor registers to the modem 204 for receiving unsolicited responses ofcoverage level change or radio coverage condition change. At block 304,the application receives information of the enhanced coverage level orradio coverage condition. At block 306, based on the receivedinformation, the application applies a restriction on sending uplinkdata. For example, the application can decide not to send uplink data ifthe modem/device is in enhanced coverage level 1, 2, or 3.

FIGS. 14A-14C show an example description of an AT command to enablesolution 1 according to some implementations. Code-points can beintroduced in one AT command from modem to application, in order tonotify the application of the radio coverage condition every time theradio coverage condition changes (i.e., unsolicited information). FIGS.14A-14C show an example change to 3GPP TS 27.007 (changes areunderlined) to introduce radio coverage information in the AT commandNetwork registration +CREG. Other AT commands could be used instead orin addition, for example PLMN selection +COPS, GPRS network registrationstatus +CGREG and/or EPS network registration status +CEREG. New ATcommands could also be created for this purpose. New fields <cov> and<cov-gsm> can be introduced in the AT command Network registration +CREGas shown in Table 2. Alternatively, <cov> and <cov-gsm> can be merged ina single field.

TABLE 2 +CREG parameter command syntax Command Possible response(s)+CREG=[<n>] +CME ERROR: <err> +CREG? +CREG: <n>, <stat>[, [<lac>],[<ci>], [<AcT>][, <cause_type>, <reject_cause>], [<cov>], [<cov-gsm>]]+CREG=? +CREG: (list of supported <n>s)

-   The fields <cov> and <cov-gsm> can include any radio coverage    information. For example, 3GPP TS 27.007 can include the following    description for the fields <cov> and <cov-gsm> for information of CE    levels and coverage classes:-   <cov>: integer type; coverage enhancement level. Applicable only if    <Act>=E-UTRAN or

0 Coverage Enhancement (CE) level 0 1 Coverage Enhancement (CE) level 12 Coverage Enhancement (CE) level 2 3 Coverage Enhancement (CE) level 3(not applicable if <Act> = NB-IoT) NOTE 7: 3GPP TS 36.331 specifiesCoverage Enhancement levels.

-   <cov-gsm>: integer type; coverage class. Applicable only if    <Act>=EC-GSM-IoT.

0 Coverage Class CC1 1 Coverage Class CC2 2 Coverage Class CC3 3Coverage Class CC4 4 Coverage Class CC5 NOTE 8: 3GPP TS 43.064 specifiesCoverage Classes.

FIGS. 24A-24B show an example of a solicited AT command according tosome implementations. For example, a new AT command can be introduced toallow the application to query the modem and the modem to reply withinformation of the radio coverage condition. FIGS. 24A-24B show anexample change to 3GPP TS 27.007 (changes are underlined) to include thenew AT command +CIOTQCEL.

Solution 2: Refraining from mobile-originated data transmission if thedevice is in enhanced coverage states: application instructs modem totransmit data conditionally.

FIG. 4 is a flow diagram 400 illustrating solution 2 for controllingdata transmission in enhanced coverage states according to someimplementations. The flow diagram 400 includes an application 202 and amodem 204 at a device. The modem 204 has knowledge of the radio coveragecondition for the device (e.g., the currently applicable CE mode/levelor coverage class, radio signal strength or quality such as RSSI, RSCP,or RSRP, a number of repetitions for data transmission, or other radiolink information). The application 202 can send an instruction 406 tothe modem 204 to instruct the modem 204 to transmit data under certainconditions. The instruction 406 can include any conditions fortransmission restrictions, and parameters associated with the conditionsfor transmission restrictions. For example, the application 202 mayinstruct the modem 204 not to send data if a device/modem CE level/modeor coverage class is one in a set of predefined CE levels/modes orcoverage classes, if a number of data repetitions is above a predefinedrepetition threshold, a signal strength at the device is below apredefined signal strength threshold, or a signal quality at the deviceis below a predefined signal quality threshold. For instance, theapplication 202 can instruct the modem 204 not to send data if themodem/device is in enhanced coverage level 1, 2, or 3. In someimplementations, the application 202 can also send data 408 to the modem204 so that the modem 204 will apply transmission restrictions on thedata 408. The instruction 406 and the data 408 can use AT commands orother APIs.

The application 202 can instruct the modem 204 to send specific uplinkdata when a device/modem CE level/mode or coverage class is not anelement of a predefined set of enhanced coverage modes/levels orcoverage classes, if a number of data repetitions is below a predefinedrepetition threshold, a signal strength at the device is above apredefined signal strength threshold, or a signal quality at the deviceis above a predefined signal quality threshold. Symmetrically, theapplication 202 can instruct the modem to not send specific uplink datawhen a device/modem CE level/mode or coverage class is an element of apredefined set of enhanced coverage modes/levels or coverage classes, ifa number of data repetitions is above a predefined repetition threshold,a signal strength at the device is below a predefined signal strengththreshold, or a signal quality at the device is below a predefinedsignal quality threshold. The specific uplink data could be senttogether with the instruction 406 (e.g., data is included in theinstruction 406), or separately (e.g., separate instruction 406 and data408). If data is sent separately from the instruction, data can bediscriminated based on, e.g. bearer identity, packet data protocol (PDP)context, application identifier, socket number (that can discriminate anapplication), or destination address. The data 408 can be sent at thesame time as the instruction 406, or at a later time. In some cases, theapplication can decide to send the data unconditionally after a numberof attempts being made aware of the coverage conditions by the modem.

Alternatively, or in combination, the application 202 can instruct themodem 204 to send any uplink data when the device/modem is not in aspecific enhanced coverage mode/level or a specific radio coveragecondition. Symmetrically, the application 202 can instruct the modem 204to not send any uplink data when the modem is in one or more specificenhanced coverage mode(s)/level(s) or a specific radio coveragecondition. Similar to solution 1, data that is not sent can either bedropped or discarded.

Table 3 lists examples of instruction 406 from the application 202 tothe modem 204. The second column of Table 3 shows whether or not therelevant uplink data is included with the instruction 406:

TABLE 3 Examples of instructions from application to modem Instructionfrom Uplink data application included with the to modem instruction Sendany uplink data if the modem is not No in enhanced coverage level 1, 2or 3 Send any uplink data if the modem is No in enhanced coverage level0 or 1 Send uplink data attached with this instruction if the Yes modemis in Coverage Class CC1 or CC2 (Other uplink data are sent withoutrestriction) Send uplink data attached Yes with this instruction if theRSSI of the Serving Cell is above 3 dB (Other uplink data are sentwithout restriction) Send uplink data related to No socket port 0 if themodem is in enhanced coverage level 0 (Other uplink data are sentwithout restriction)Other conditions can also be used, for example, applying a transmissionrestriction for more stringent enhanced coverage modes/levels orcoverage classes, such as enhanced coverage level 3.

FIG. 5 is a flowchart illustrating a first example method 500 forsolution 2 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 500 starts at block 502,where the application sends specific data to the modem and instructs themodem to apply a restriction on sending this data according to theconditions specified in the instruction. At block 504, the modem appliesa transmission restriction on the data according to the instruction. Forexample, the application can instruct the modem to apply a transmissionrestriction on the data if the modem/device is in enhanced coveragelevel 1, 2, or 3. Accordingly, the modem does not send the specific dataif the modem/device is in enhanced coverage level 1, 2, or 3.

FIG. 6 is a flowchart illustrating a second example method 600 forsolution 2 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 600 starts at block 602,where the application instructs the modem to apply a restriction onsending any future data coming from port 0. At block 604, the modemapplies a transmission restriction on the data from port 0 according tothe instruction. For example, the application can instruct the modem toapply a transmission restriction on data from port 0 if the modem/deviceis in enhanced coverage level 1, 2, or 3. Accordingly, the modem doesnot send data from port 0 if the modem/device is in enhanced coveragelevel 1, 2, or 3.

FIGS. 15A-15B show a first example description of an AT command toenable solution 2 according to some implementations. FIGS. 15A-15B showan example change to 3GPP TS 27.007 (changes are underlined) to send aninstruction and related data in an AT command. A new field <cond> can beintroduced in the AT command +CSODCP as shown in Table 4. Theapplication can include the instruction in the filed <cond> and thespecific data in the field <cpdata>.

TABLE 4 +CSODCP action command syntax Command Possible Response(s)+CSODCP=<cpdata_length>, +CME ERROR: <err> <cpdata>[, <RAI>[,<type_of_user_data>, <cond>]] +CSODCP=? +CSODCP: (maximum number ofbytes of the <cpdata_length>), (list of supported <type_of_user_data>s)The field <cond> can include any instruction. For example, 3GPP TS27.007 can include the following description for the field <cond> if theinstruction relates to CE levels/coverage classes:

-   <cond>: integer type. Indicates the condition for transmitting the    user data.    -   0 Transmit the data    -   1 Transmit the data only if the device is not in Coverage        Enhancement (CE) levels 1, 2, and 3 (E-UTRAN or NB-IoT)        -   Transmit the data only if the device is not in Coverage            Class 2, 3 and 4 (EC-GSM-IoT)-   NOTE 7: 3GPP TS 36.331 specifies Coverage Enhancement levels. 3GPP    TS 43.064 specifies Coverage Classes.

Alternatively, the field <cond> can include an instruction related tothe maximum CE level or the highest coverage class in which the userdata shall be transmitted. For example, 3GPP TS 27.007 can include thefollowing description for the field <cond>: <cond>: integer type.Specifies the maximum Coverage Enhancement (CE) level 0 to 3 (E-UTRAN),0 to 2 (NB-IoT) or the highest Coverage Class 1 to 5 (EC-GSM-IoT; CC1 toCC5, respectively) in which the user data shall be transmitted. If theCE level or the coverage class, as applicable, is above the valueindicated, the user data shall not be transmitted.

As another alternative, 3GPP TS 27.007 can include the followingdescription for the field <cond> if the instruction relates to CElevels/coverage classes and a predefined timer for transmissionrestrictions:

-   <cond>: integer type. Indicates the condition for transmitting the    user data.    -   0 Transmit the data    -   1 Transmit the data only if:    -   E-UTRAN or NB-IoT:        -   The device is in Coverage Enhancement (CE) level 0; or        -   The device is in Coverage Enhancement (CE) level 1, 2 or            (applicable to E-UTRAN only) 3, and the data was not            transmitted for the last hour.    -   EC-GSM-IoT:        -   The device is in Coverage Class CC1; or        -   The device is in Coverage Class CC2, CC3, CC4 or (if            applicable) CC5, and the data was not transmitted for the            last hour.

Solutions 1 and 2 can be used when the device is in idle mode orconnected mode, and can be used in conjunction at different times.

Additional or alternative condition for refraining frommobile-originated data transmission based on data type

Alternatively, or in combination, data type can be used as a conditionfor transmission restrictions in solutions 1 and/or 2. For instance,some types of data are less critical from a system point of view thanothers. Examples of such type of data may be data specific to a givenapplication or type of use (as more than one application on the devicecan use the same type of data for different purposes). Alternatively,some data may be time sensitive, and there is no value in sending themif the transmission has to be delayed (as the enhanced coveragefunctionality introduces further delays by using a large number ofrepeated transmissions). Therefore, the application could refrain fromsending uplink data (e.g. one or more uplink message(s)) if the deviceis in an enhanced coverage state, with an additional condition based ondata type.

For example, data related to device location may be a condition forrefraining of sending uplink data, whereas data related to a flat tireissue would not be a condition for refraining of sending uplink data.Data related to emergency (e.g. emergency call information, imminentcar-crash information, or emergency location information) would not be acondition for refraining of sending uplink data, while other uplink datawould. In another example, data packets related to transmission controlprotocol (TCP)/Internet protocol (IP) could be refrained from beingsent, while data packets related to constrained application protocol(COAP)/user data protocol (UDP)/IP could be sent. The reason is thatTCP/IP might not work well with enhanced coverage due to additionaldelays. In some cases, the additional condition can relate to IP addressand/or port number (socket), Access Point Name (APN), or protocolrelated information (e.g. evolved packet system (EPS) bearer for LTE orPDP context for 2G/3G, which discriminate the user plane session).

Other examples of different data types or sub-types that could triggertransmission restrictions can include (but not limited to): fleetmanagement and logistics, automotive telematics, automation andmonitoring, point of sales (PoS), security and surveillance, healthmonitoring (e.g., machine-to-machine healthcare gateway, wearablehealthcare monitoring devices, or (wearable) wellness/fitness servicedevices), secure remote patient care and monitoring, wearables (e.g.,video streaming, file sharing, or gaming), smart building (e.g.,analytics, lighting, fire and life safety, or security and access),energy (e.g., wide area energy related measurement/control system foradvanced transmission and distribution automation, analytics use casefor machine-to machine such as initiate and stop collection, conditionalcollection, create/modify collection scheme, smart reader reading,environmental monitoring of remote locations to determine hydropower,and/or oil and gas pipeline cellular/satellite), enterprise (e.g., smartbuilding such as building automation and control or analytics orlighting, fire and life safety/security and access, heating,ventilation, air conditioning, power and energy, and/or industrialsystems), public service (e.g., street light automation, use case ondevices, virtual devices and things, and/or car/bicycle sharingservices), residential (e.g., home energy management, home energymanagement system, plug-in electrical charging vehicles and power feedin home scenario, real-time audio/video communication, event triggeredtask execution use case, and/or semantic home control), semantic deviceplug and play, agriculture (e.g., remote equipment monitoring, remotecrop monitoring, climate monitoring and forecasting, predictiveanalytics for crops and livestock, livestock tracking and geofencing,statistics on livestock feeding and produce, smart logistics andwarehousing, and/or drone monitoring and control), telematics (vehiclediagnostic and maintenance report and services, traffic accidentinformation collection, stolen vehicle recovery, roadside assistance,in-car entertainment and internet access, vehicle navigation,usage-based insurance, lease, rental, and/or HP and share carmanagement), transportation (e.g., fleet management service usingdigital tachograph), others (e.g., extending the machine-to-machineaccess and/or network using satellites, M2M data traffic management byunderlying network operator, optimized M2M interworking with mobilenetworks, optimizing connectivity management parameters, optimizingmobility management parameters, sleepy node use case, use case oncollection of M2M system data, leveraging broadcasting/multicastingcapabilities of underlying networks, and/or leveraging serviceprovisioning for equipment with built-in machine-to-machine device).Note that the device 102 can be devices using these example data typesand use cases.

Alternatively, or in combination, quality of service (QoS) can be usedas a condition for transmission restrictions in solutions 1 and 2. Forexample, if the device is in an enhanced coverage state, uplink datacould be sent if the device is configured with one or more bearer thatcan cope with the delay caused by the repeated transmissions of theenhanced coverage functionality, or the one or more bearer that has aQoS associated with:

-   -   Guaranteed Bit Rate (GBR);    -   non-GBR (non-GBR might tolerate delays due to repeated        transmissions); and/or    -   certain QoS Class identifier(s) (QCI(s)), for example, QCIs        reflecting a bearer that is interactive.

-   The above examples use LTE QoS terminology. Other terminologies are    possible with the example of other RATs. For example, for 2G/3G    systems, the condition could be that the QoS traffic class(es) for    the active PDP context(s) is(are) conversational or streaming. Other    possible criteria can be related to priority levels such as:    -   ‘High priority’ and/or ‘normal priority’ versus ‘low priority’        in the precedence class.    -   ‘Priority 1’ (highest) and/or ‘Priority 2’ versus ‘priority 3’        in the radio priority of the data bearer.

FIG. 7 is a flowchart illustrating a second example method 700 forsolution 1 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 700 starts at block 702,where the application inquires the modem, e.g., using an AT command,about the radio coverage condition. Block 702 is optional if theapplication subscribes or registers to the modem for receivingunsolicited responses of radio coverage condition change. At block 704,the application receives information of the radio coverage condition. Atblock 706, based on the received information, the application can applya restriction on sending uplink data. For example, the application candecide not to send uplink data if the modem or device is in enhancedcoverage level 1, 2, or 3 and the data relates to non-emergency devicelocation information.

FIG. 8 is a flowchart illustrating a third example method 800 forsolution 2 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 800 starts at block 802,where the application instructs the modem to apply a restriction onsending future uplink data according to the conditions specified in theinstruction. At block 804, the modem applies a restriction on uplinkdata transmission according to the instruction. For example, theapplication instructs the modem to apply a transmission restriction onuplink data if the modem/device is in enhanced coverage level 1, 2, or 3and the data relates to non-emergency device location information.Accordingly, the modem does not send uplink data if the modem/device isin enhanced coverage level 1, 2, or 3 and the data relates tonon-emergency device location information.

In some cases, different applications control different uplink data, anda scenario of different applications sending conflicting instructions isunlikely to happen. However, if this happens, some rules can be definedfor the overall decision. For example:

-   -   the latest instruction received in time can apply for the modem;        or    -   some precedence control can be introduced within the        instruction(s). For example, a number can be assigned to each        instruction from the application to the modem. In case of        conflict, the instruction with the highest number is applied.        Some default values can be used.    -   some predefined rules can apply for the modem. For example, data        sent by application(s) not using a transmission restriction with        a set of conditions cannot be prevented to be sent by        application(s) using the transmission restriction with the same        set of conditions.

FIG. 16 shows a second example description of an AT command to enablesolution 2 according to some implementations. A new AT command can beintroduced from the application to the modem to carry the instructionwhere data is not sent together with the instruction. FIG. 16 show anexample change to 3GPP TS 27.007 (changes are underlined) to include thenew AT command +CEUDR. Table 5 shows the new AT command +CEUDR.

TABLE 5 +CEUDR parameter command syntax Command Possible response(s)+CEUDR=[<setting>] +CEUDR? +CEUDR: <setting> +CEUDR=? +CEUDR: (list ofsupported <setting>s)The new AT command +CEUDR can include any instruction. For example, 3GPPTS 27.007 can include the following description for the new AT command+CEUDR if the instruction relates to CE levels/coverage classes and apredefined timer for transmission restrictions:Description

The set command is used to set the MT to operate according to uplinkdata restriction.

The read command returns the usage setting set by the TE.

The test command is used for requesting information on the supported MTsetting(s).

Defined Values

-   -   <setting>: integer type; indicates the uplink data restriction        for the MT. The default value is manufacturer specific.        -   0 uplink data for socket port 0 allowed to be sent        -   1 uplink data for socket port 0 allowed to be sent if:        -   E-UTRAN or NB-IoT:            -   The device is in Coverage Enhancement (CE) level 0; or            -   The device is in Coverage Enhancement (CE) level 1, 2 or                (applicable to E-UTRAN only) 3, and the data was not                transmitted for the last hour.        -   NOTE 1: 3GPP TS 36.331 specifies Coverage Enhancement            levels.        -   EC-GSM-IoT:            -   The device is in Coverage Class CC1; or            -   The device is in Coverage Class CC2, CC3, CC4 or (if                applicable) CC5, and the data was not transmitted for                the last hour.        -   NOTE 2: 3GPP TS 43.064 specifies Coverage Classes.            Implementation

Optional.

Additional or alternative condition for refraining frommobile-originated data transmission based on wait time duration and/ornumber of attempts

Alternatively, or in combination, the transmission restrictions insolutions 1 and 2 can be based on a time duration and/or a number ofattempts exceeding a threshold. The threshold can be pre-defined, orconfigurable as discussed below. In other words, refraining from sendingone or more specific message(s) or data would apply for a predefinedtime duration and/or a specific number of messages. For example, afterthe application has refrained from sending uplink message(s) due to thedevice is in an enhanced coverage state, it could revoke the refraining(i.e. send message(s) again) if messages have been prevented to be sent,e.g., for a time duration exceeding a predefined threshold. As anotherexample, the application can instruct the modem to refrain from sendingthe data if the device is in an enhanced coverage state. After a certainwait time has expired, the application can send another instructionindicating that data will be sent unconditionally with respect to theradio coverage condition.

In some cases, if uplink messages are sent repetitively (e.g.,periodically sending location information), the device can refrain fromsending uplink messages for a specific number of messages or sendingopportunities if the device is in an enhance coverage state (e.g., thedevice is in one or more specific enhanced coverage level(s)/mode(s)).After the specific number of uplink messages have been refrained frombeing sent or the specific number of sending opportunities have beenrefrained from being used, the device can send one uplink message evenif the device is still in an enhanced coverage state and uses extrabattery power for the uplink transmission. Depending on the applicationtriggering the uplink messages, the data content that has not been sentcan be sent later when the transmission restriction is revoked, or thedata content can be dropped (e.g., location information that becomesobsolete after some time duration).

Additional or alternative condition for refraining frommobile-originated data transmission based on device location/speed

As an additional or alternative condition for solutions 1 and 2, theapplication can refrain from sending one or more specific message(s) ordata if the device is moving. For example, after the application(solution 1) or modem (solution 2) has held transmission of uplink datadue to the device is in an enhanced coverage state, the transmissionrestriction can be revoked if the device stops moving, or stops movingduring at least a certain duration. For example, in the case of sendinglocation information, it can be useful for the network to know that thedevice has become stationary and in which location. Therefore, exceptionto the “not sending uplink data” can be made when the device becomesstationary, and uplink data (e.g. one message) can be sent even if itwould use extra battery in an enhanced coverage state. In some cases,exception to the “not sending uplink data” can be made when the devicehas remained stationary for more than a certain time duration. In otherwords, the transmission restriction may not be revoked if the truckstops then restarts immediately, e.g., at a stop sign.

For another example, when the device is in an enhanced coverage state,it can be beneficial to allow the sending of uplink data (e.g., locationor emergency information) if a lorry is entering a predefined area(e.g., based on location information from a location sensor such as GPS,or the Cell Identity, the Routing Area, or Tracking Area Identity of thedevice or any other identified geographical zone known by the network)associated with, for example, a dodgy area in a town. In other words,the device refrains from sending uplink messages if the device is in anenhanced coverage state and the device is not in a dodgy area. In somecases, when an application uses location information, it can bebeneficial for the application server to know that the device has becomestationary and at which location. The transmission restriction can berevoked when the device becomes stationary, and a limited amount ofuplink data (e.g., one uplink message) can be sent even if it would useextra battery in enhanced coverage states. For example, after one uplinkmessage has been sent, sending of uplink message(s) can be preventedagain even though the device is still stationary.

In some cases, if the application knows that the device was in anenhanced coverage state beforehand (e.g., based on the last time thatthe application queried the modem), and if the application knows thedevice has not moved (e.g., via accelerometer reading), the applicationmay not wake the modem up for assessing or inquiring the enhancedcoverage modes/levels if a non-critical event occurs, because theapplication knows that the device is still in the enhanced coveragestate. In other words, the application can refrain from querying themodem. Avoiding the modem assessing the enhanced coverage level can savefurther battery, because it avoids switching on some electroniccomponents in the device/modem.

FIG. 9 is a second flow diagram 900 illustrating solution 1 forcontrolling data transmission in enhanced coverage states according tosome implementations. The flow diagram 900 includes an application 202,a modem 204, and a location sensor or an accelerometer 902 at a device.The modem 204 has knowledge of the radio coverage condition for thedevice. The application 202 can send a query 206 to the modem 204 forinformation or status of the radio coverage condition and receive astatus report 208 from the modem 204. The application 202 can also senda query 908 to the location sensor or the accelerometer 902 and receivea response 910 including location and/or speed information. Based on thestatus report 208 and the response 910, the application 202 determineswhether to send uplink data or not. For example, the application 202 candecide not to transmit uplink data if the enhanced coverage level is 1,2, or 3 and the device is moving. Note that the query/statusinteractions between the application 202 and the modem 204 and betweenthe application 202 and the location sensor or accelerometer 902 canhappen in any order (i.e., query the location sensor or accelerometer902 first and then the modem 204, or the opposite), or simultaneously.

For solution 2, the modem itself may obtain device location/speedinformation and does not need to query a location sensor oraccelerometer. For example, the modem can obtain the location/speedinformation by analyzing received GPS signals at the modem, analyzingreceived radio signals from base stations, or using radio cellularmethods such as Cell Identity. In some implementations, as shown in FIG.4, the application can send an instruction and related data to themodem, where the instruction could be “send this data (1) if the modemis not in an enhanced coverage state or (2) if the modem is in anenhanced coverage state and the device is not moving.” After receivingthe data and the instruction, based on the location/speed informationthe modem can apply the transmission restriction accordingly.

Additional or alternative condition for refraining frommobile-originated data transmission based on battery level

An additional or alternative condition for solutions 1 and 2 can bebased on battery level. For example, for solution 1, the applicationwill refrain from sending specific uplink data in enhanced coveragestates if the battery level is below a first threshold and/or is above asecond threshold. Thresholds can be in percentage, e.g., 100% means thebattery is completely full and 0% means the battery is not usable.

The reason for sending data (or data of a certain type/relevance) in anenhanced coverage state if the battery level is above a first thresholdis that transmitting the corresponding data is beneficial from a systempoint of view and would not jeopardize the battery life (e.g., thebattery level is deemed sufficient to last until it can berecharged/replaced). On the other hand, if the battery level is belowthe first threshold, it might be preferred to not send the correspondingdata and keep the battery power for sending the most relevant orcritical data.

The reason for sending data in an enhanced coverage state if the batterylevel is below a second threshold is that it might be preferred to usean eventual opportunity to send relevant/critical uplink data. Forexample, when the device battery is about to run out of power in a shorttimeframe, it might be preferable for the device to send a locationmessage to the network, e.g., indicating that “I am located here and mybattery is dying,” while the location message would not be sent if thebattery is above the second threshold.

FIG. 10 is a third flow diagram 1000 illustrating solution 1 forcontrolling data transmission in enhanced coverage states according tosome implementations. The flow diagram 1000 includes an application 202,a modem 204, and an operating system, a device interface, or a batterysensor 1002 at a device. For example, the device interface can be a ManMachine Interface (MMI). The modem 204 has knowledge of the radiocoverage condition for the device. The application 202 can send a query206 to the modem 204 for information or status of the radio coveragecondition and receive a status report 208 from the modem 204. Theapplication 202 can also send a query 1008 to the operating system, thedevice interface, or the battery sensor 1002 and receive a response 1010including information on the battery level or battery status. Based onthe status report 208 and the response 1010, the application 202determines whether to send uplink data or not. For example, theapplication 202 can decide not to transmit uplink data if the enhancedcoverage level is 1, 2, or 3 and the battery level is below a firstthreshold and above a second threshold. Note that the query/statusinteractions between the application 202 and the modem 204 and betweenthe application 202 and the operating system, device interface, orbattery sensor 1002 can happen in any order (i.e., query the operatingsystem, device interface, or battery sensor 1002 first and then themodem 204, or the opposite), or simultaneously.

For solution 2, the application can send an instruction and related datato the modem. For example, the instruction can be “send this data (1) ifthe modem is not in an enhanced coverage state or (2) if the modem is inan enhanced coverage state and the battery level is above 80% or below5%.” The modem can send a query to the operating system, deviceinterface, or battery sensor for battery level information. Based on thebattery level information from the operating system, device interface,or battery sensor and the instruction from the application, the modemwill apply transmission restrictions accordingly.

The query to the operating system, device interface, or battery sensorcan include one or more battery threshold. For example, the query can be“is the battery level below 5%” or “provide the battery level.” Theresponse from the operating system, device interface, or battery sensorcan include status with respect to one or more battery threshold, e.g.,whether the battery level is below a first threshold, or whether thebattery level is above a second threshold. The response can also includeabsolute battery level, e.g., voltage, current, or electric charge (inCoulombs) level.

Additional or alternative condition for refraining frommobile-originated data transmission based on whether the device isplugged in a power supply

An additional or alternative condition for solutions 1 and 2 can bebased on whether the device is plugged in a power supply. For example,for solution 1, the application will refrain from sending uplink data inenhanced coverage states if the device is not plugged in an electricitypower outlet. In other words, a device in an enhanced coverage statewill send uplink data if the device is plugged in a power outlet wherepower consumption becomes less of an issue. Similar to querying thebattery level, the application or the modem can query the operatingsystem, device interface, or battery sensor whether the device isplugged in a power supply.

In some cases, the transmission restriction in enhanced coverage statescan be applied based on a combination of radio coverage condition, datatype, QoS, a predefined time period, a predefined number of attempts,device location/speed, battery level, and/or whether the device isplugged in a power supply.

FIG. 11 is a flowchart illustrating a third example method 1100 forsolution 1 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 1100 applies transmissionrestrictions based on the radio coverage information, device speedinformation, battery level, whether the device is plugged in a powersupply, and a predefined time period. The method 1100 starts at block1102, where the application inquires the modem, e.g., using an ATcommand, about radio coverage condition, inquires the location sensor oraccelerometer about the device's speed, and inquires the operatingsystem, device interface, or battery sensor for the battery level andwhether the device is plugged in a power supply. Block 1102 is optionalif the application already has the information. At block 1104, theapplication receives information of the radio coverage condition,battery level, location/speed information, and whether the device isplugged in a power supply. At block 1106, based on the receivedinformation, the application applies a restriction on sending uplinkdata. For example, the application can decide not to send uplink datafor one hour if the data relates to non-emergency location information,the modem or device is in enhanced coverage level 1, 2, or 3, the deviceis moving (or the device is not moving and one message has already beensent at the current location), the device is not plugged in a powersupply, and the battery level is above one threshold and below anotherthreshold.

FIG. 12 is a flowchart illustrating a fourth example method 1200 forsolution 2 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 1200 applies transmissionrestrictions based on the radio coverage condition, device speed, and apredefined time period. The method 1200 starts at block 1202, where theapplication sends specific data to the modem and instructs the modem toapply a restriction on sending this data according to the conditionsspecified in the instruction. At block 1204, the modem applies atransmission restriction on the data according to the instruction. Forexample, the application can instruct the modem to apply a transmissionrestriction on the data for one hour if the device is in enhancedcoverage level 1, 2, or 3 and the device is moving, and the modem willapply the transmission restriction accordingly.

FIG. 13 is a flowchart illustrating a fifth example method 1300 forsolution 2 of controlling data transmission in enhanced coverage statesaccording to some implementations. The method 1200 applies transmissionrestrictions based on the radio coverage condition, device speed, and apredefined time period. The method 1300 starts at block 1302, where theapplication instructs the modem to apply a restriction on sending anyfuture data coming from port 0. At block 1304, the modem applies atransmission restriction on the data from port 0 according to theinstruction. For example, the application can instruct the modem toapply a transmission restriction on data from port 0 for one hour if thedevice is in enhanced coverage level 1, 2, or 3 and the device ismoving, and the modem will apply the transmission restrictionaccordingly.

In some implementations, the device, the device upper layer, or anapplication in the device can be configured as to whether thetransmission restriction in enhanced coverage states is allowed or not.If the transmission restriction is allowed, the device or theapplication can be further configured with parameters associated withthe conditions of the transmission restriction. For example, the deviceor the application can be configured with parameters such as whether thetransmission restriction is allowed or not, the time period for thetransmission restriction, the data type impacted by the transmissionrestriction, battery levels associated with the transmissionrestriction, etc. In some implementations, the network can force thedevice to apply transmission restrictions.

Several methods can be used to configure the transmission restriction insolutions 1 and 2. The first method is to pre-define the configurationparameters in the device. For example, the configuration parameters canbe pre-set by the device manufacturer or set by a user of the devicethrough a user interface. In some cases, the device may also derive theconditions for transmission restrictions based on some signalingparameters from the network. As an example, the device can determine theconditions based on the QoS class of the traffic or the logical channelor the radio bearer to which the traffic belongs to, etc.

The second method is to specify the configuration parameters in industrystandards so that the device operation will comply with the industrystandards. For example, 3GPP standards can specify the conditions fortransmission restrictions by including a sentence such as “Transmituplink data only if the device is not in Coverage Enhancement (CE)levels 1, 2, and 3.”

The third method is that the network sends configuration parameters tothe device. Refraining from transmitting data until coverage improvesmay impact traffic QoS and as such, the network is responsible forensuring a given QoS. Hence, it is possible that the network would liketo control when a given set of conditions may be used for transmittingdata belonging to a specific traffic (or QoS) class. For example,transmission restrictions can be applied for some QoS classes, but notfor other QoS classes. In some cases, transmission restrictions can beapplied for some applications, but not for other applications. Thenetwork may send the configuration parameters related to transmissionrestrictions in a downlink control message (or in a system informationmessage) to the device (e.g., at Access Stratum level via point-to-pointsignaling or point-to-multipoint broadcast signaling, or a Non-AccessStratum message), so that the transmission restriction functionality atthe device is controlled and configurable by the network. The networkmay also send the configuration parameters via the USIM applicationtoolkit (USAT) application or Open Mobile Alliance (OMA) devicemanagement (DM). For example, the network can configure the followingparameters for the device:

-   -   Take battery level into consideration for uplink data sending        restriction (yes/no) (i.e., the network can configure the device        whether or not to take battery level into consideration for        uplink data transmission restrictions),    -   Allow uplink data sending restriction if the battery is less        than 90% charged (yes/no),    -   Allow uplink data sending restriction if the battery is more        than 10% charged (yes/no),    -   Take into account whether the device is connected on main power        for uplink data sending restriction (yes/no),    -   Use predefined location area for uplink data sending restriction        (yes/no),    -   Use list of defined location areas for uplink data sending        restriction (yes/no),    -   Uplink data sending restriction is allowed (yes/no),    -   Uplink data sending restriction allowed if the device is in        enhanced coverage level 3 (yes/no),    -   Uplink data sending restriction allowed if the device is in        enhanced coverage level 2 or 3 (yes/no),    -   Uplink data sending restriction allowed for a maximum of one        hour (yes/no),    -   Uplink data sending restriction allowed with maximum holding of        a specific uplink data for three hours (yes/no),    -   Uplink data sending restriction allowed for periodic location        information reporting for a maximum of five messages (yes/no),    -   Uplink data sending restriction allowed for traffic mapped to        certain (indicated) traffic class (or QoS class or radio        bearer/logical channel/logical channel group),    -   Uplink data sending restrictions are not allowed (i.e. such data        should be sent immediately regardless of other conditions) for        certain (indicated) traffic class (or QoS class or radio        bearer/logical channel/logical channel group),    -   Maximum delay restrictions for a given traffic class.

As discussed above, the network can send configuration parametersrelated to transmission restrictions in a downlink control message. Thedownlink message could be at Non-Access Stratum (NAS) level, forexample, using messages in LTE NAS Layer 3 protocol (see 3GPP TS 24.301)for LTE NB-IoT UEs. In some cases, the configuration parameters can beadded in the Tracking Area Accept message or Attach Accept message fromthe network to the device. Alternatively, or in addition, theconfiguration parameters can be added in the Protocol ConfigurationOptions (PCO) information element (IE) using the EPS bearer contextactivation procedure that involve downlink message coming from packetdata network (PDN) Gateway or Service Capability Exposure Function(SCEF) within the network, towards the UE. Other procedures that involvedownlink messages that carry the PCO IE and that could be used forincluding configuration parameters after enhancing the content of thePCO IE are the EPS bearer context deactivation procedure, EPS bearercontext modification procedure, PDN connectivity reject procedure,bearer resource allocation reject procedure, and bearer resourcemodification reject procedure. Downlink messages such as ActivateDefault EPS Bearer Context Request message, Activate Dedicated EPSBearer Context Request message, ESM Information Request message, andModify EPS Bearer Context Request message can be used to include theconfiguration parameters for transmission restrictions. For GSM,messages in 3GPP TS 24.008 can be used instead (e.g. Routing Area Acceptmessage, or Attach Accept message). The PCO IE can be used again as itis also sent in downlink GSM messages, e.g. Activate PDP Context Acceptmessage, Activate Secondary PDP Context Reject message, Request PDPContext Activation message, Modify PDP Context Request message, ModifyPDP Context Accept message, and Modify PDP Context Reject message.

FIG. 17 shows an example IE or field including configuration informationfor transmission restrictions according to some implementations. The IEor field 1700 can be included in a downlink message for sendingtransmission restriction configuration parameters to the device. Forexample, the IE or field 1700 can include the following description:

Data Sending Indication value

-   Uplink Data Restriction Allowed (UDRA)-   Bits-   2 1-   0 0 No information available-   0 1 Uplink data sending restriction not allowed-   1 0 Uplink data sending restriction allowed for a maximum of one    hour if the UE is in Enhanced coverage 1, 2 or 3-   1 1 Uplink data sending restriction allowed for a maximum of two    hours if the UE is in Enhanced coverage 1, 2 or 3

FIGS. 18A-18D show a first example description of includingconfiguration parameters for transmission restrictions in an AttachAccept message according to some implementations. FIGS. 18A-18D show anexample change to 3GPP TS 24.301 (changes are underlined), where thetransmission restriction is applied based on radio coverage conditionsand a predefined time period. For example, 3GPP TS 24.301 can includethe following description (also shown in FIG. 18A):

If the ATTACH ACCEPT message includes the Data Sending Indication IE,this indicates to the UE if it is allowed to apply uplink data sendingrestriction and for which duration. 3GPP TS 24.301 can also include anew IE of data sending indication in Attach Accept message as shown inTable 6 (also shown in FIG. 18C).

TABLE 6 data sending indication IE in Attach Accept message InformationType/ IEI Element Reference Presence Format Length x- Data sending Datasending O TV 1 indication indication3GPP TS 24.301 can include the description for the data sendingindication IE as shown in FIGS. 18C-18D.

FIG. 19 shows a second example description of including configurationparameters for transmission restrictions in an Attach Accept messageaccording to some implementations. FIG. 19 shows an example change to3GPP TS 24.301 (changes are underlined), including the description forthe IE Data Sending Indication discussed in FIGS. 18A-18D where thetransmission restrictions can be applied based on radio coverageconditions, a predefined time period, battery level, whether the deviceis moving, and whether the device is plugged in a power supply.

FIGS. 20A-20H show an example description of including configurationparameters for transmission restrictions in an Activate Default EPSBearer Context Request message according to some implementations. The IEExtended Protocol Configuration Options in the Activate Default EPSBearer Context Request message (shown in FIG. 20C) from 3GPP TS 24.301can be used to include the configuration parameters. Because thecontents of the extended protocol configuration options are specified in3GPP TS 24.008, FIGS. 20D-20H show an example change to 3GPP TS 24.008(changes are underlined). For example, FIG. 20G shows that theconfiguration protocol can include a new parameter list “0017H (UplinkData Restriction Indication).” FIGS. 20G-20H show an example descriptionfor the new parameter list of uplink data restriction indication, wherethe transmission restriction can be applied based on radio coveragecondition, a predefined time period, battery level, whether the deviceis moving, and whether the device is plugged in a power supply.

Alternatively, or in combination, other downlink messages can be usedfor sending configuration parameters of transmission restrictions to thedevice. For example, messages at an Access Stratum level viapoint-to-point signaling or point-to-multipoint broadcast signaling. Insome cases, when the device is in an RRC idle mode, SIB messages couldbe used to include the configuration parameters. Alternatively, or inaddition, when the device is in an RRC Connected mode, messages such asthe RRCConnectionSetup, RRCConnectionReconfiguration, orRRCConnectionResume message can be used to include the configurationparameters.

FIG. 21 shows an example RRC IE including configuration information oftransmission restrictions according to some implementations. FIG. 21shows an example change to 3GPP TS 36.331 (changes are underlined),where a new IE can be included. FIG. 21 shows an example description forthe new IE UL-DataRestrictions, where the transmission restriction canbe applied to certain logical channels based on a battery level and apredefined time period. The IE UL-DataRestrictions can be included inthe following RRC IEs which can be included in RRC messages:radioResourceConfigDedicated, radioResourceConfigCommon, orSystemInformationBlockType2.

Alternatively, or in combination, the downlink message of a USATapplication for Home Public Land Mobile Network (PLMN) can be used tosend the configuration parameters of transmission restrictions. This canupdate files that are stored in the (U)SIM and specified in 3GPP TS31.102. This can be used to configure the application or the device.Similar codings as shown in FIGS. 14A-21 and FIGS. 24A-24B can be used.Other messages, possibly applying to other systems than GSM/GPRS/LTE orother 3GPP systems, can be used. The network can instruct thedevice/application on the following aspects:

-   -   Whether to refrain transmitting uplink message is allowed or        not.    -   Validity conditions as whether to refrain or not (time durations        and/or number of messages used to decide to refrain). For        example, the device may be configured to not transmit one or        more uplink message(s) based on a number of repetitions        threshold, that would compare to the number of repetitions        configured by the network, e.g., for a specific channel.    -   Which QoS associated with uplink messages allows or not to send        the uplink message.    -   Whether the additional condition of battery level shall apply or        not. If this applies, what is the battery threshold to be used.

FIG. 22 is a schematic illustrating an example network node 2200according to some implementations. The illustrated network node 2200includes a processing module 2202, a wired communication subsystem 2204,and a wireless communication subsystem 2206. The wireless communicationsubsystem 2206 can receive data traffic and control traffic fromdevices. In some implementations, the wireless communication subsystem2206 may include a receiver and a transmitter. The wired communicationsubsystem 2204 can be configured to transmit and receive controlinformation between other access node devices via backhaul connections.The processing module 2202 can include one or more processing components(alternatively referred to as “processors” or “central processing units”(CPUs)) capable of executing instructions related to one or more of theprocesses, steps, or actions described above in connection with one ormore of the implementations disclosed herein. The processing module 2202can also include other auxiliary components, such as random accessmemory (RAM), read only memory (ROM), secondary storage (for example, ahard disk drive, flash memory or other non-transitory storage medium).The processing module 2202 can execute certain instructions and commandsto provide wireless or wired communication, using the wiredcommunication subsystem 2204 or a wireless communication subsystem 2206.Various other components can also be included in the network node 2200.

FIG. 23 is a schematic illustrating an example UE device 2300 accordingto some implementations. The example device 2300 includes a processingunit 2302, a computer-readable storage medium 2304 (for example, ROM orflash memory), a wireless communication subsystem 2306, an interface2308, and an I/O interface 2310. The processing unit 2302 can includeone or more processing components (alternatively referred to as“processors” or “central processing units” (CPUs)) configured to executeinstructions related to one or more of the processes, steps, or actionsdescribed above in connection with one or more of the implementationsdisclosed herein. The processing unit 2302 can also include otherauxiliary components, such as random access memory (RAM) and read onlymemory (ROM). The computer-readable storage medium 2304 can be embodiedby a non-transitory medium configured to store an operating system (OS)of the device 2300 and various other computer-executable softwareprograms for performing one or more of the processes, steps, or actionsdescribed above.

The wireless communication subsystem 2306 may be configured to providewireless communications for data information or control informationprovided by the processing unit 2302. The wireless communicationsubsystem 2306 can include, for example, one or more antennas, areceiver, a transmitter, a local oscillator, a mixer, and a digitalsignal processing (DSP) unit. In some implementations, the subsystem2306 can support multiple input multiple output (MIMO) transmissions. Insome implementations, the receivers in the wireless communicationsubsystems 2306 can be an advance receiver or a baseline receiver. Tworeceivers can be implemented with identical, similar, or differentreceiver processing algorithms.

The user interface 2308 can include, for example, one or more of ascreen or touch screen (for example, a liquid crystal display (LCD), alight emitting display (LED), an organic light emitting display (OLED),a microelectromechanical system (MEMS) display), a keyboard or keypad, atrackball, a speaker, and a microphone. The I/O interface 2310 caninclude, for example, a universal serial bus (USB) interface. A skilledartisan will readily appreciate that various other components can alsobe included in the example device 2300.

It will be appreciated by those skilled in the art that a similarprocess could be applied for mobile terminated messages. In this case anapplication server or Services Capability Server (SCS) can receiveinformation from the cellular network indicative of the radio coveragecondition of a device. The application server or SCS can then use thisinformation to determine whether or not to forward the mobile terminatedmessage towards the cellular network, and can take into account similarcriteria such as those listed for the uplink case. Criteria could forexample include data type, QoS indicator, priority level, timer expiry,counter threshold, battery level and UE mobility. The application serveror SCS could receive the radio coverage condition information from thenetwork through a variety of means, for example it could query thenetwork prior to sending each mobile terminated message or it couldconfigure an event on the cellular network so that the applicationserver or Services Capability Server is informed every time there is achange in the radio coverage condition, where in this latter case somehysteresis might also be applied in the reporting. These queries andevent configurations could be achieved using signaling between theapplication server or Services Capability Server (SCS) and the ServiceCapability Exposure Function (SCEF) [3GPP TS 23.682]. The ServiceCapability Exposure Function could in turn determine informationindicative of the radio coverage condition of the device from themobility management entity (MME) via the T6a interface or from theserving GPRS support node (SGSN) via the T6b interface. The MME in turncould be informed of radio coverage condition from the BTS, Node B, orevolved Node B (eNB) or through signaling from the UE. Up to dateinformation on radio coverage condition may only be available in thenetwork when the UE has entered connected mode. During the periods wherethe UE is operating in idle mode, the cellular network may only be ableto return a last known radio coverage condition, possibly along with atime stamp corresponding to when that information was acquired.

While operations are depicted in the drawings in a particular order,this should not be understood as requiring that such operations beperformed in the particular order shown or in sequential order, or thatall illustrated operations be performed, to achieve desirable results.In certain circumstances, multitasking and parallel processing may beemployed. Moreover, the separation of various system components in theimplementation descried above should not be understood as requiring suchseparation in all implementations, and it should be understood that thedescribed program components and systems can generally be integratedtogether in a signal software product or packaged into multiple softwareproducts.

Also, techniques, systems, subsystems, and methods described andillustrated in the various implementations as discrete or separate maybe combined or integrated with other systems, modules, techniques, ormethods. Other items shown or discussed as coupled or directly coupledor communicating with each other may be indirectly coupled orcommunicating through some interface, device, or intermediate component,whether electrically, mechanically, or otherwise. Other examples ofchanges, substitutions, and alterations are ascertainable by one skilledin the art and may be made.

While the above detailed description has shown, described, and pointedout the fundamental novel features of the disclosure as applied tovarious implementations, it will be understood that various omissions,substitutions, and changes in the form and details of the systemillustrated may be made by those skilled in the art. In addition, theorder of method steps is not implied by the order they appear in theclaims.

The invention claimed is:
 1. A method, comprising: receiving, by anapplication running on a user equipment (UE), information indicative ofa radio coverage condition; based on the received information,determining that the UE is in a certain coverage state; and in responseto the determining, controlling uplink data transmission, wherein thecontrolling uplink data transmission comprises refraining from sendinguplink data when at least one of the following occurs: the UE is in oneof a set of predefined coverage enhancement levels, coverage classes, orcoverage enhancement modes, a data repetition indicator at the UE isabove a predefined repetition threshold, a signal strength at the UE isbelow a predefined signal strength threshold, or a signal quality at theUE is below a predefined signal quality threshold; the uplink data has apredefined data type; the uplink data is associated with at least one ofa predefined Quality of Service (QoS) indicator, a predefined prioritylevel, or a predefined bit rate information; a predefined timerassociated with the uplink data transmission has not expired; a counterassociated with the uplink data transmission has reached a predefinedcounter threshold; the UE is moving; a battery level of the UE is higherthan a first threshold; a battery level of the UE is lower than a secondthreshold; or the UE is not plugged into a power outlet.
 2. The methodof claim 1, wherein the received information comprises at least one of acoverage enhancement level, a coverage enhancement mode, a coverageclass, a data repetition indicator, a signal strength, or a signalquality.
 3. The method of claim 1, further comprises: receiving speedinformation from a location sensor or an accelerometer of the UE; andbased on the speed information, determining whether the UE is moving. 4.The method of claim 2, wherein receiving speed information is responsiveto a query sent by the application to the location sensor or theaccelerometer.
 5. The method of claim 1, further comprising: receivingbattery information from an operating system, a device interface, or abattery sensor of the UE; and based on the battery information,determining whether the battery level of the UE is higher than the firstthreshold or lower than the second threshold, or whether the UE isplugged into a power outlet.
 6. The method of claim 5, wherein receivingbattery information is responsive to a query sent by the application tothe operating system, the device interface, or the battery sensor. 7.The method of claim 1, further comprising: receiving, at the UE and froma network node, configuration information including an indication thatthe UE is configured to control uplink data transmission and parametersassociated with controlling the uplink data transmission.
 8. The methodof claim 1, wherein receiving information indicative of a radio coveragecondition is responsive to a query sent by the application.
 9. Themethod of claim 8, wherein the query for information indicative of aradio coverage condition is conveyed in a first attention (AT) command.10. The method of claim 1, wherein the information indicative of a radiocoverage condition is conveyed in a second AT command.
 11. The method ofclaim 1, further comprising: receiving information indicative of a radiocoverage condition when the radio coverage condition changes.
 12. A userequipment (UE), comprising: a memory; and at least one hardwareprocessor communicatively coupled with the memory and configured to::receive, by an application running on the UE, information indicative ofa radio coverage condition; based on the received information, determinethat the UE is in a certain coverage state; and in response to thedetermining, control uplink data transmission, wherein the controllinguplink data transmission comprises refraining from sending uplink datawhen at least one of the following occurs: the UE is in one of a set ofpredefined coverage enhancement levels, coverage classes, or coverageenhancement modes, a data repetition indicator at the UE is above apredefined repetition threshold, a signal strength at the UE is below apredefined signal strength threshold, or a signal quality at the UE isbelow a predefined signal quality threshold; the uplink data has apredefined data type; the uplink data is associated with at least one ofa predefined Quality of Service (QoS) indicator, a predefined prioritylevel, or a predefined bit rate information; a predefined timerassociated with the uplink data transmission has not expired; a counterassociated with the uplink data transmission has reached a predefinedcounter threshold; the UE is moving; a battery level of the UE is higherthan a first threshold; a battery level of the UE is lower than a secondthreshold; or the UE is not plugged into a power outlet.
 13. The UE ofclaim 12, wherein the received information comprises at least one of acoverage enhancement level, a coverage enhancement mode, a coverageclass, a data repetition indicator, a signal strength, or a signalquality.
 14. The UE of claim 12, wherein the at least one hardwareprocessor is further configured to: receive speed information from alocation sensor or an accelerometer of the UE; and based on the speedinformation, determine whether the UE is moving.
 15. The UE of claim 14,wherein the speed information is received in response to a query sent bythe application to the location sensor or the accelerometer.
 16. The UEof claim 12, wherein the at least one hardware processor is furtherconfigured to: receive battery information from an operating system, adevice interface, or a battery sensor of the UE; and based on thebattery information, determine whether the battery level of the UE ishigher than the first threshold or lower than the second threshold, orwhether the UE is plugged into a power outlet.
 17. The UE of claim 12,wherein the at least one hardware processor is further configured to:receive, at the UE and from a network node, configuration informationincluding an indication that the UE is configured to control uplink datatransmission and parameters associated with controlling the uplink datatransmission.
 18. The UE of claim 12, wherein the information indicativeof a radio coverage condition is conveyed in a second AT command. 19.The UE of claim 12, wherein the at least one hardware processor isfurther configured to: receive information indicative of a radiocoverage condition when the radio coverage condition changes.
 20. Atangible, non-transitory computer-readable medium containinginstructions which, when executed, cause a user equipment (UE) toperform operations comprising: receiving, by an application running onthe UE, information indicative of a radio coverage condition; based onthe received information, determining that the UE is in a certaincoverage state; and in response to the determining, controlling uplinkdata transmission, wherein the controlling uplink data transmissioncomprises refraining from sending uplink data when at least one of thefollowing occurs: the UE is in one of a set of predefined coverageenhancement levels, coverage classes, or coverage enhancement modes, adata repetition indicator at the UE is above a predefined repetitionthreshold, a signal strength at the UE is below a predefined signalstrength threshold, or a signal quality at the UE is below a predefinedsignal quality threshold; the uplink data has a predefined data type;the uplink data is associated with at least one of a predefined Qualityof Service (QoS) indicator, a predefined priority level, or a predefinedbit rate information; a predefined timer associated with the uplink datatransmission has not expired; a counter associated with the uplink datatransmission has reached a predefined counter threshold; the UE ismoving; a battery level of the UE is higher than a first threshold; abattery level of the UE is lower than a second threshold; or the UE isnot plugged into a power outlet.